Method and logic for capturing and analyzing conduit data

ABSTRACT

A method of locking data and a program that analyzes the data commences with a generation of a first key. This first key is associated with both the data and a specific, compiled copy of the program. A gatekeeper logic is generated. The gatekeeper logic utilizes at least the first key to prevent the specific, compiled copy of the program from analyzing data other than the specific data. In this way, the specific copy of the program is locked to specific data, and is accordingly limited to performing analysis operations utilizing the specific data.

RELATED APPLICATION

The present patent application is a continuation of U.S. applicationSer. No. 09/657,759, filed Sep. 8, 2000, entitled METHOD AND LOGIC FORCAPTURING AND ANALYZING CONDUIT DATA, which is a continuation-in-part ofU.S. application Ser. No. 09/340,216, filed Jun. 25, 1999, now U.S. Pat.No. 6,658,567 issued Dec. 2, 2003, entitled METHOD AND LOGIC FOR LOCKINGGEOLOGICAL DATA AND AN ANALYZER PROGRAM THAT ANALYZES THE GEOLOGICALDATA.

The above-referenced applications are hereby incorporated herein byreference.

FIELD OF THE INVENTION

The present invention relates generally to the field of software anddata distribution and, more specifically to the distribution of data andan associated analyzer program that analyzes the data to provideevaluations and assessments, the analyzer program being limited toanalysis of the specific data.

BACKGROUND OF THE INVENTION

Pipelines are commonly used in the transportation of oil and gas. Thereare more than 300,000 miles of oil and gas pipelines in North America.Construction costs are now of the order of $1,000,000 per mile. Thetypical initial operating life of the pipelines are expected to be about40 years, but 50% of the of the existing pipelines will be 40 years oldat the year 2000.

Accurate monitoring of the pipelines is critical due to the potentialrisks to the environment when the pipelines rupture and due to the highcosts of repair or replacement. Since oil and gas pipelines are normallyburied, in-service inspection is performed by pumping a “smartelectronic inspection pig” through the pipeline from one compressorstation to the next.

Generally, the inspection tool detects and collects data indicatingabnormalities (e.g., leakage, corrosion or metal loss) in the internaland external pipe surface or wall. The inspection tool may providedetailed signals about the condition of the pipelines. The signals arethen converted to accurate estimates of defect size and geometry. Thisrequires considerable expertise, as well as a detailed understanding ofthe effects of inspection conditions and the behavior of the type ofpipeline steel used.

The information collected by the smart electronic inspection pig can beanalyzed by an evaluation or analyzer software. The information can alsobe stored on a storage device such as, for example, a compact disc (CD)and can then be readily available for further analysis. The analyzersoftware typically reads large volumes of data generated during theinspection. The analyzer software may include a graphical userinterface. Using the data collected during the inspection, the analyzersoftware may generally perform some data analysis and generates writtenand electronic reports or some form of graphical display.

Pipeline inspection activities or survey are generally performed byconsulting firms such as pipeline assessment services performing boththe data collection activity and the data analysis activity. Anintelligent pig-based survey is expensive and may cost some hundreds ofthousand of dollars, with certain long distance, more complicated linesbeing charged well in excess of this.

It would be cost advantageous if the user of the pipeline inspectiondata, (e.g., an oil company) could be enabled to have control of boththe pipeline inspection data and the analyzer program that analyze thepipeline inspection data. This way the inspection data can be analyzedas often as desired and at any time as desired. However, the cost of ananalyzer program may be prohibitively expensive and economicallyunattractive.

SUMMARY OF THE INVENTION

According to one embodiment of the invention, there is provided a methodof locking a specific data and an analyzer program that analyzes thespecific data. A first key is generated and associated with the specificdata and a specific copy of the analyzer program. A gatekeeper logic isgenerated. The gatekeeper logic utilizes at least the first key toprevent the specific copy of the analyzer program from analyzing anyother data except for the specific data.

According to another embodiment of the invention, there is provided amethod of locking a specific conduit data with a specific copy of ananalyzer program that analyzes the specific conduit data. A first key isgenerated and associated with both the specific conduit data and thespecific copy of the analyzer program. A gatekeeper logic is generated.The gatekeeper logic utilizes at least the first key to prevent thespecific copy of the analyzer program from analyzing any other conduitdata except for the specific conduit data.

Other features of the present invention will be apparent from theaccompanying drawings and from the detailed description which follows.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and notlimitation in the figures of the accompanying drawings, in which likereferences indicate similar elements and in which:

FIG. 1 is a block diagram illustrating an exemplary system for lockingconduit data and an analyzer program that analyzes the conduit data.

FIG. 2 is a flow chart illustrating a method, according to an exemplaryembodiment of the present invention, of locking conduit data and ananalyzer program so that a specific copy of the analyzer program isenabled to analyze only specific conduit data.

FIG. 3A is a flow chart illustrating a method, according to an exemplaryembodiment of the present invention, of executing an analyzer program toanalyze conduit data to which it is locked.

FIG. 3B is a flow chart illustrating an alternative method, according toan exemplary embodiment of the present invention, of executing ananalyzer program to analyze conduit data to which it is locked.

FIGS. 4A-4C illustrate methods, according to alternative embodiments ofthe present invention, of distributing conduit data and an analyzerprogram that analyzes the conduit data to an end user of the conduitdata conduit data conduit data and the analyzer program.

FIG. 5 is a flow chart illustrating a method, according to an exemplaryembodiment of the present invention, that may be performed by a conduitassessment service provider, an end user, and an analyzer programsoftware supplier to implement the method illustrated in FIGS. 4A-4C.

FIG. 6 is a flow chart illustrating a method, according to an exemplaryembodiment of the present invention, of distributing conduit data and ananalyzer program to an end user.

FIG. 7 is a block diagram illustrating a machine, in the exemplary formof a computer system, within which a set of instructions for causing thecomputer system to perform any of the methodologies discussed above maybe executed.

DETAILED DESCRIPTION

A method and logic for locking conduit data and an analyzer program thatanalyzes the conduit data are described. In the following description,for purposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of the present invention. Itwill be evident, however, to one skilled in the art that the presentinvention may be practiced without these specific details.

For the purposes of the present invention, the term “conduit” shallrefer to any opening or cavity enclosed or surrounded by a structurehaving features, conditions or characteristics of a pipeline orpipeline-like environment such as, for example, an oil or gas pipeline,a sewer or other utility pipeline, a well or a bore hole. The structuremay be generally vertical or horizontal or may form any angles with theground level. The structure may be above ground, under ground, in land,under water, or any combination of these. Further, the term “data” shallbe taken to include, but not limited to geomechanical, geophysical, insitu stress, petrophysical, geotechnical, acoustic wave form, magneticwave resonance, vibration data, digital data or any other data derivedusing a logging device within the structure. The logging device may be adevice that collects data such as, for example, a pig inspection device.

For the purposes of the present specification, the term “analyzerprogram” shall be taken to refer to any program that analyzes data forthe purpose of presenting, interpreting or modifying the data.Accordingly, the operations performed by an analyzer program include,but are not limited to, the extraction of data, the generating of data,the interpretation of data, the display of data, the filtering of data,and the enhancing of data.

FIG. 1 is a block diagram illustrating a system 10, according to anexemplary embodiment of the present invention, for locking conduit dataand an analyzer program that analyzes the conduit data. The system 10includes conduit data files 12 that may, for example, comprise loggedacoustic data, electrical data, optical data, digital data, magneticdata or vibration data. The conduit data files 12 are inputted to anencryption or locking routine 14 that operates to lock the conduit datafiles 12 to a specific copy of an analyzer program. This enables thespecific copy of the analyzer program only to analyze the specificconduit data files 12, and no other conduit data files. To this end, thelocking routine 14 includes a random number generator 16 that generatesa first key 18, which in one embodiment of the present inventioncomprises a simple random number. In another embodiment, the first key18 may comprise any random character sequence.

The locking routine 14 also operates to identify a specificcharacteristic of each of the conduit data files 12, and to assign acharacteristic value to a characteristic parameter indicative of theparticular characteristic of each conduit data file 12. For example, thecharacteristic parameter may be the size of a conduit data file 12, andthe characteristic value attributed to this parameter may be actual sizeof a conduit data file 12 expressed in bits, bytes or any other measure.

Further, the locking routine 14 generates a second key 22 for each ofthe conduit data files 12, which is associated with a respective conduitdata file 12, utilizing the first key and the characteristic value for arespective file 12. For example, the logging routine 14 may simplyexclusive OR (XOR), the first key and the characteristic parameter togenerate the second key 22. The locking routine 14 then writes arespective second key 22 into a header portion of each of the files 12,as illustrated in FIG. 1. Alternatively, the second key 22 may beinserted into the conduit data files 12 in a manner that is not soeasily discernable. For example, the second key 22 may be fractured intopieces that are inserted at predetermined locations throughout theconduit data files 12 by the locking routine 14.

Further, the locking routine 14 generates a gatekeeper application 24,in the exemplary form of a Java™ applet, which implements an “unlocking”function with respect to the conduit data files 12 and a specific copyof an analyzer program. This is to permit the analyzer program toanalyze the conduit data files. Further information regarding thegatekeeper application 24 is provided below.

A compiler 28 compiles the source code 26 of the analyzer program togenerate a specific compiled copy of the analyzer application 30 thatincorporates the first key 18 and the gatekeeper application 24. Thesource code 26 for the analyzer program can be provided by a softwaredeveloper such as, for example, the GMI-Imager software developed byGeoMechanics International, Incorporated of Palo Alto, Calif.

The conduit data files 12 and the compiled analyzer application 30 maytogether comprise a single package 32 that is supplied to an end user.For example, the conduit data files 12 and the compiled copy of theanalyzer application 30 may be written to a single compact disk (e.g.,CD) that is supplied to the end user. Alternatively, the conduit datafiles 12 and the specific copy of the analyzer application 30 may bepropagated to an end user from a source over a network.

In one embodiment, a single first key 18 may be utilized by the lockingroutine 14 to generate multiple distinct second keys 22 for each of theconduit data files 12. This may be achieved by performing an operationutilizing the first key 18 and a specific characteristic value for eachdistinct file of the conduit data files 12 to generate a distinct secondkey 22 for each such distinct conduit data file. Accordingly, thepackage 32 may comprise a single copy of the compiled analyzerapplication 30 that is able to analyze each of the multiple conduit datafiles 12, each having a different and unique second key 22.

FIG. 2 is a flow chart illustrating a method 34, according to anexemplary embodiment of the present invention, of locking conduit dataand an analyzer program so that a specific copy of the analyzer programis enabled to analyze only the specific conduit data.

The method commences at block 36, with the generation of the first key18 by the random number generator 16. At block 38, the locking routine14 generates the gatekeeper application 24 that is to be compiled withthe analyzer application source code 26 (e.g., the analyzer program). Atblock 40, the locking routine 14 determines a characteristic value for acharacteristic parameter of at least one conduit data file 12. Asdiscussed above, the locking routine 14 may determine a respectivecharacteristic value for a number of conduit data files 12. Thecharacteristic value may be, for example, the size of a respectiveconduit data file.

At block 42, the locking routine 14 then generates a respective secondkey 22 for each conduit data file 12 utilizing the first key 18 and therespective characteristic value 19 for the respective conduit data file12. For example, the second key 22 may be generated for the respectiveconduit data file 12 by performing an exclusive-or (XOR) operationbetween the first key 18 and the characteristic value 19 for eachrespective conduit data file 12.

At block 44, the locking routine 14 incorporates the second key 22 intothe header of each respective conduit data file 12. As discussed above,in an alternative embodiment, a second key 22 for each respectiveconduit data file 12 may be distributed throughout the file 12 atpredetermined and known locations. At block 46, the compiler 28 thencompiles the analyzer application source code 26 together with the firstkey 18 and the gatekeeper application 24 and generates a specificcompiled copy of the analyzer application 30. At block 48, the specificcompiled copy of the analyzer application 30 and the conduit data files12 that the analyzer application can access and analyze, are supplied tothe end user as the package 32. The method 34 then ends at block 50.

FIG. 3A is a flow chart showing a method 52, according to an exemplaryembodiment of the present invention, of executing an analyzer program toanalyze conduit data to which it is locked.

The method 52 commences at block 54, with the initiation or launch by anend user of the specific compiled copy of the analyzer application 30shown in FIG. 1 and supplied to the user at block 48 of the method 34illustrated in FIG. 2. At block 56, the gatekeeper application 24 beginsexecution and it identifies the first key 18 within the specific copy ofthe analyzer application 30. At block 60, the gatekeeper application 24opens the conduit data files 12 and, at block 62, determines acharacteristic value for a characteristic parameter of each of theconduit data files 12. For example, the gatekeeper application 24 mayascertain the size of each of the conduit data files 12.

At block 64, the gatekeeper application 24 calculates a gate key foreach of the conduit data files 12 utilizing the first key identified atblock 58 and the respective characteristic value for characteristicparameter for each of the conduit data files 12. The calculation of thegate key is the same as the calculation of the second key 22 describedin FIG. 1 and at block 42 of FIG. 2. For example, the gate key may becalculated by performing a XOR operation utilizing the first key 18 andthe determined characteristic value for the characteristic parameter foreach of the conduit data files 12.

At decision block 66, a determination is made as to whether the gate keygenerated for each of the conduit data files 12 corresponds to arespective second key 22 stored, for example, in the header portion ofthe respective conduit data file 12. Following a positive determinationat decision box 66, for a specific conduit data file 12, the gatekeeperapplication 24 enables analysis of the specific conduit data file 12 bythe specific copy of the analyzer application 30. On the other hand,following a negative determination for a specific conduit data file 12at decision box 66, the gatekeeper application 24 disables the specificcopy of the analyzer application 30 from analyzing the relevant datafile 12. The negative determination occurs when the user attempt to usethe specific copy of the analyzer application with a conduit data fileother than the conduit data files 12. The method 52 then ends at block72.

FIG. 3B is a flow chart illustrating an alternative method 74, accordingto an exemplary embodiment of the present invention, of executing ananalyzer program to analyze conduit data to which it is locked.

The method 74 corresponds substantially to the method 52 discussed abovewith respect to FIG. 3A. They are different in that at block 76, thegatekeeper application 24 identifies the second key 22 of a specificconduit data file 12, and then at block 78 calculates the gate keyutilizing this second key 22 and the characteristic value of therelevant file 12. At decision box 80, the gatekeeper application 24makes a determination as to whether the gate key corresponds to thefirst key 18 embedded within the specific copy of the analyzerapplication 30. This decision is to determine whether or not thespecific copy of the analyzer application 30 will be enabled to analyzethe relevant conduit data file 12.

In summary, the methods 52 and 74 differ in that, in the method 52, thefirst key 18 is utilized together with the characteristic parameter todetermine the gate key which is then compared to the second key 22stored within the conduit data file 12. In the method 74, the second key22 is utilized to generate the gate key, that is then compared to thefirst key 18 embedded within the compiled and specific copy of theanalyzer application 30.

FIGS. 4A-4C illustrate methods 90, 92 and 94, according to alternativeembodiments of the present invention, of distributing conduit data andan analyzer program that analyzes the conduit data to the end user ofthe conduit data and the analyzer program.

Referring first to FIG. 4A, conduit data 98 may be provided by a conduitinspection service company 96 such as, for example, BlackHawk PipelineAssessment Services of Atlanta, Ga., to the end user 100. Conduit data98 may be stored on a compact disk (CD) 99. The end user 100 thenprovides the conduit data 98 on the CD 99 to the analyzer softwaresupplier 102.

Having received the conduit data 98 from the end user 100, the analyzersoftware supplier 102 will then proceed, utilizing the locking (orencryption) routine 14 to compile the analyzer application source code26 to include the conduit data 98 and the locking (or encryption)routine 14 to thereby generate the package 32. As described above withreference to FIG. 1, the package 32 comprises object code thatconstitutes a compiled specific copy of the analyzer application 30, andone or more conduit data files 12. The gatekeeper application 24, inconjunction with the first and second keys 18 and 22, constitutes a lock104 illustrated in FIG. 4A. The package 32 may be written to a compactdisk 107, that is then supplied back to the end user 100.

Utilizing the compact disk 107, the end user 100 may then execute theanalyzer application 30 to analyze only the conduit data 98. Except forthe conduit data 98, the compiled analyzer application 30 will not workwith any other conduit data.

The above-discussed method 90 of distribution of the locked compiledanalyzer application 30 and conduit data 98 is advantageous to theanalyzer software supplier 102. The analyzer software supplier 102 isable to incrementally recover the cost of the analyzer application bysupplying multiple copies of an analyzer application 30 to the end user100. Each analyzer application copy is locked to the specific conduitdata 98. Each compiled and specific copy of the analyzer application 30is supplied at a reduced price relative to the cost of supply of anunencumbered or “unlocked” analyzer program that is not limited to thespecific conduit data 98, and that would be able to analyze any givenconduit data. By supplying numerous copies of compiled specific analyzerapplications 30 to the end user, the analyzer software supplier 102 willthus be able to generate a steady revenue flow from the end user 100 andrecover a “full” price for the program over time.

From the point of view of the end user 100, the distribution method 90discussed above with reference to FIG. 4A is advantageous. Instead ofbeing required to buy an “unlocked” copy of the analyzer program 26 fora relatively high (and sometimes unaffordable) cost, the end user 100incurs incremental and time-distributed costs for use of the analyzerprogram. A further benefit to the end user 100 is that the distributionmethod 90 implements an alternative to a “pay-per-use” system. Thisprovides advantages in that the cost to the end user 100 of the analyzerapplication 30 is linked to the usage and value to the company of thespecific conduit data 98.

FIG. 4B shows an alternative method 92 of distributing conduit data andan analyzer program that analyzes the conduit data to an end user 100.The method 92 corresponds substantially to the method 90 with referenceto FIG. 4A. However, instead of the conduit data 98 being propagatedbetween the conduit inspection service company 96, the end user 100 andthe analyzer software supplier 102 on a compact disk, the relevant dataand applications are transmitted via a network (not shown). The networkmay be a wire or wireless, and may comprise the Internet, a Wide AreaNetwork (WAN) or a Local Area Network (LAN). The method 92 may providesome cost advantages over the method 90, and may also be more convenientin certain circumstances.

FIG. 4C shows a further method 94 of distributing conduit data and ananalyzer program, which are locked, to an end user 100. While theconduit inspection service company 96 provides the conduit data 98 tothe end user 100, as in the methods 90 and 92 above, this conduit data98 is not provided to the analyzer software supplier 102. In the method94, the analyzer software supplier 102 provides a further package 108 tothe end user 100, the package 108 including a copy-protected andread-protected copy of the analyzer application source code 26, a copyof the locking routine 14, and a purge routine 106. The end user 100then executes the locking routine 14 to enable the analyzer application30 locally to generate the first key 18, the gatekeeper application 24and the second key 22. Following compilation of a specific and compiledcopy of the analyzer application 30, and the embedding of the second key22 within a conduit data file 12, the purge routine 106 will thenautomatically be invoked to purge the locking routine 14 and theanalyzer application source code 26 from a computer system operated bythe end user 100. The end user 100 will then retain only the package 32,the other software having been purged from a relevant computer system bythe purge routine 106.

The method 94 illustrated in FIG. 4C is advantageous in that it is notrequired that the conduit data 98 be provided from the end user 100 tothe analyzer software supplier 102. On the other hand, the generation ofthe locked analyzer application 30 and conduit data 98 at an end-usersite may be undesirable, and may be unattractive to an end user 100.

FIG. 5 is a flow chart illustrating the steps performed by the conduitinspection service company 96, the end user 100 and the analyzersoftware supplier 102 as described above with reference to FIG. 4. Atblock 110, the conduit data 98 is provided to the analyzer softwaresupplier 102 from the conduit inspection service company 96 via the enduser 100. At block 112, the analyzer software supplier 102 then locksthe analyzer application 30 to the conduit data 98. At block 114, theanalyzer software supplier 102 supplies the locked analyzer application30 and conduit data 98 to the end user 100. At block 116, the gatekeeperapplication 24, embedded within the analyzer application 30, allows auser to execute the locked software to analyze only the specific conduitdata 98.

The method 90 described above with reference to FIG. 5 also embodies theprocesses performed when executing the method 92 discussed above withreference to FIG. 4B.

FIG. 6 is a flow chart illustrating a method 94, according to anexemplary embodiment of the present invention, of distributing conduitdata and an analyzer program to an end user. The method 94 is performedby the conduit inspection service company 96, the end user 100 and theanalyzer software supplier 102.

At block 120, the end user 100 acquires the conduit data 98 from theconduit inspection service company 96. At block 112, the end user 100requests an analyzer application source code 26, which is copy and readprotected, to the end user 100. The supplier 102 also provides thelocking routine 14 and purge routine 106. At block 126, the end user 100then executes the locking routine 14 to lock the conduit data 98 to aspecific and compiled copy of the analyzer application 30. This mayinvolve generating the gatekeeper application 24, and performing acompile operation utilizing a compiler 28 as described with reference toFIG. 1.

At block 128, the locking routine 14 calls the purge routine 106 topurge the locking routine and the analyzer application source code 26from the computer system of the end-user 100. At block 130, thegatekeeper application 24 allows the end user 100 to execute theanalyzer application 30 to analyze the conduit data 98, and no otherconduit data, to which is locked. The method 94 then ends at block 132.

FIG. 7 is a block diagram illustrating a machine, in the exemplary formof a computer system 140, within which a set of instructions, forcausing the computer system 140 to perform any one of the methodologiesdiscussed above, may be executed. The computer system 140 includes aprocessor 142, a main memory 144, and a static memory 146 thatcommunicate with each other via a bus 148. The computer system 140further includes a video display unit 149 (e.g., a liquid crystaldisplay (LCD) or a cathode ray tube (CTR)). The computer system 140further includes an alpha-numeric input device 150 (e.g., a keyboard), acursor control device 152 (e.g., a mouse), a disk drive unit 154, asignal generation device 156 (e.g., a speaker) and a network interfacedevice 158.

The disk drive unit 154 includes a machine-readable medium 160 on whichis stored a set of instructions (i.e., software 162) embodying any one,or all, of the methodologies discussed above. The software 162 is alsoshown to reside, completely or at least partially, within the mainmemory 144 and/or within the processor 142. The software 162 mayfurthermore be transmitted or received via the network interface device158.

For the purposes of this specification, the term “machine-readablemedium” shall be taken to include any medium which is capable of storingor embodying a sequence of instructions for execution by the machine andthat cause the machine to perform any one of the methodologies of thepresent invention. The term “machine-readable medium” shall accordinglybe taken to included, but not be limited to, solid-state memories,optical and magnetic disks, and carrier wave signals.

Thus, a method and logic for locking conduit data and an analyzer dataprogram that analyzes the conduit data have been described. Although thepresent invention has been described with reference to specificexemplary embodiments, the present invention can also be practiced withany analyzer program being locked with any respective data to providethe end users the same advantages discussed above. For example, a salesperson can purchase marketing data for a specific region locked togetherwith an analyzer program that provides analyses of the same marketingdata

It will be evident that various modifications and changes may be made tothese embodiments without departing from the broader spirit and scope ofthe invention. Accordingly, the specification and drawings are to beregarded in an illustrative rather than a restrictive sense.

1. A method of locking data obtained with a logging device and ananalyzer program that analyzes the data, the method including:generating a first key; associating the first key with both specificdata obtained with the logging device and a specific copy of theanalyzer program; and generating gatekeeper logic that enables thespecific copy of the analyzer program to analyze the specific data onlyif the first key associated with the specific copy of the analyzerprogram corresponds with a second key associated with the specific dataobtained with the logging device.
 2. The method of claim 1 wherein thegenerating of the first key includes generating a random charactersequence.
 3. The method of claim 2 wherein the random character sequenceis a random number sequence.
 4. The method of claim 1 wherein theassociating of the first key with the specific copy of the analyzerprogram includes compiling the specific copy of the analyzer program toincorporate the first key.
 5. The method of claim 1 wherein thegenerating of the gatekeeper logic includes associating the gatekeeperlogic with the specific copy of the analyzer program.
 6. The method ofclaim 5 wherein the associating of the gatekeeper logic with thespecific copy of the analyzer program includes compiling the specificcopy of the analyzer program to incorporate the gatekeeper logic.
 7. Themethod of claim 1 wherein the generating of the gatekeeper logiccomprises generating a Java-programming language application that isincorporated within the specific copy of the analyzer program.
 8. Themethod of claim 1 wherein a user of the analyzer program supplies thespecific data obtained with the logging device to a supplier of theanalyzer program, and a locking of the specific data obtained with thelogging device to the specific copy of the analyzer program occurs on acomputer system of the supplier.
 9. The method of claim 8 wherein thesupplier provides the locked specific data obtained with the loggingdevice and the specific copy of the analyzer program to the user. 10.The method of claim 1 wherein a supplier of the analyzer programsupplies locking logic and the analyzer program to a user of theanalyzer program, and a locking of the specific data, obtained with thelogging device, to the specific copy of the analyzer program occurs on acomputer system of the user utilizing the supplied locking logic and thesupplied analyzer program.
 11. A method of distributing data obtainedwith a logging device and an analyzer program that analyzes the data,the method including: providing a user of the analyzer program with aspecific copy of the analyzer program and specific data, obtained withthe logging device, that are locked utilizing at least a first key; andproviding the user of the analyzer program with gatekeeper logic thatenables the specific copy of the analyzer program to analyze dataobtained with the logging device only if the first key associated withthe analyzer program corresponds with a second key associated with thespecific data obtained with the logging device.
 12. The method of claim11 wherein the providing of the gatekeeper logic includes compiling thespecific copy of the analyzer program to include the gatekeeper logic,and providing the user with the compiled specific copy of the analyzerprogram.
 13. The method of claim 11 wherein the providing of thespecific copy of the analyzer program and the specific data obtainedwith the logging device includes associating the first key with both thespecific copy of analyzer program and the specific data obtained withthe logging device.
 14. The method of claim 11 wherein the associatingof the first key with the specific copy of the analyzer program includescompiling the specific copy of the analyzer program to include the firstkey.
 15. A method of distributing data obtained with the logging deviceand an application program that accesses the data, the method including:locking a specific copy of the application program to specific dataobtained with the logging device so that the specific copy of theapplication program is able to access only the specific data, obtainedwith the logging device, having an associated key that corresponds witha second key associated with the specific copy of the applicationprogram; and distributing the locked specific copy of the applicationprogram and specific data obtained with the logging device to a user.16. The method of claim 15 wherein the locking of the specific copy ofthe application program to the specific data obtained with the loggingdevice includes generating a first key that is associated with both thespecific copy of the application program and the specific data obtainedwith the logging device.
 17. The method of claim 16 wherein thegenerating of the first key comprises generating a random key utilizinga random character generator.
 18. The method of claim 16 wherein thegenerating of the first key comprises generating a random number using arandom number generator.
 19. The method of claim 15 wherein the lockingof the specific copy of the application program to the specific dataobtained with the logging device includes generating a gatekeeperapplication that allows utilization of the specific copy of theapplication program when accessing the specific data obtained with thelogging device, and disallows utilization of the application programwhen accessing other data obtained with the logging device.
 20. Themethod of claim 15 wherein the locking of the specific copy of theapplication program to the specific data obtained with the loggingdevice includes compiling source code for the application program,together with the first key and the gatekeeper application, intocompiled object code for the specific copy of the application program.21. The method of claim 20 including distributing the gatekeeperapplication to the user, the gatekeeper application accessing at leastthe first key for the purposes of allowing or disallowing utilization ofthe specific copy of the application program.
 22. The method of claim 15wherein the locking is performed by locking logic, and the methodincludes sending the specific data obtained with the logging device fromthe user to a software supplier, the software supplier executing thelocking logic to lock the specific copy of the application program tothe specific data obtained with the logging device so that the specificcopy of the application program is able to access only the specific dataobtained with the logging device.
 23. The method of claim 15 includingsending the locked specific copy of the application program and specificdata obtained with the logging device from the user to the softwaresupplier.
 24. The method of claim 23 wherein the sending comprisespropagating the specific data obtained with the logging device over acommunications network.
 25. The method of claim 23 wherein the sendingcomprises supplying the software supplier with a physical storage mediumthat stores the specific data obtained with the logging device.
 26. Themethod of claim 15 wherein the locking is performed by locking logic,the method includes sending the locking logic and the applicationprogram from a software supplier to the user, the user executing thelocking logic to lock the specific copy of the application program tothe specific data obtained with the logging device so that the specificcopy of the application program is able to access only the specific dataobtained with the logging device.
 27. The method of claim 26 includingpurging the locking logic from a computer system of the user subsequentto the locking of the specific copy of the application program to thespecific data obtained with the logging device.
 28. The method of claim27 wherein the sending comprises propagating the locking logic and theapplication program over a communications network.
 29. The method ofclaim 27 wherein the sending comprises supplying the user with aphysical storage medium that stores the locking logic and theapplication program.
 30. A logic set for locking data obtained with alogging device and an analyzer program that analyzes the data, the logicset including: first logic to generate a first key; second logic toassociate the first key with both specific data obtained with thelogging device and a specific copy of the analyzer program; and thirdlogic to generate gatekeeper logic that enables the specific copy of theanalyzer program to analyze data obtained with the logging device onlyif the first key associated with the specific copy of the analyzerprogram corresponds with a second key associated with the data obtainedwith the logging device.
 31. The logic set of claim 30 wherein the firstlogic comprises a random number generator.
 32. The logic set of claim 30wherein the second logic comprises a compiler that compiles the specificcopy of the analyzer program to incorporate the gatekeeper logic
 33. Thelogic set of claim 30 wherein the second logic comprises a compiler thatcompiles the specific copy of the analyzer program to incorporate thefirst key.
 34. The logic set of claim 30 wherein the third logiccomprises a locking routine.
 35. Apparatus for locking data obtainedwith a logging device and an analyzer program that analyzes the data,the apparatus including: first means for generating a first key; secondmeans for associating the first key with both specific data obtainedwith the logging device and a specific copy of the analyzer program; andthird means for generating gatekeeper logic that enables the specificcopy of the analyzer program to analyze data obtained with the loggingdevice only if the first key associated with the analyzer programcorresponds with a second key associated with the data obtained with thelogging device.
 36. A machine-readable medium having a sequence ofinstructions stored thereon that, when executed by a machine, cause themachine to perform the steps of: generating a first key; associating thefirst key with both specific data obtained with a logging device and aspecific copy of an analyzer program; and generating gatekeeper logicthat enables the specific copy of the analyzer program to analyze thespecific data obtained with the logging device only if the first keyassociated with the analyzer program corresponds with a second keyassociated with the specific data obtained with the logging device. 37.A machine-readable medium having a sequence of instructions storedthereon that, when executed by a machine, cause the machine, in responseto a user request received over a communications network, to perform thesteps of: automatically providing, over the communications network, auser of the analyzer program with a specific copy of the analyzerprogram and specific data obtained with a logging device that are lockedutilizing at least a first key; and automatically providing, over thecommunications network, the user of the analyzer program with gatekeeperlogic that enables the specific copy of the analyzer program to analyzedata obtained with the logging device only if the first key associatedwith the analyzer program corresponds with a second key associated withthe specific data obtained with the logging device.
 38. Amachine-readable medium having a sequence of instructions stored thereonthat, when executed by a machine, cause the machine, in response to auser request received over a communications network, to perform thesteps of: automatically locking a specific copy of an applicationprogram to specific data obtained with a logging device so that thespecific copy of the application program is able to access only thespecific data obtained with the logging device having an associated keythat corresponds with a key associated with the specific copy of theapplication program; and automatically distributing the locked specificcopy of the application program and specific data obtained with thelogging device to a user.